System and method for third-party-service-assisted chatbot workflow execution

ABSTRACT

The flexibility of a communication with a chatbot can be increased using a chatbot platform that can be integrated with a plurality of chat channels as well as facilitate communication between users of different chat channels. The platform can host chatbots that can leverage a plurality of resources, including internal and external natural language processors, machine learning, analytics services, and third party services to generate a response to user communications and take actions on behalf of the user. The use of the natural language processing and other additional information allows to generate an appropriate response to user queries, and to thus increase the speed with which user concerns are address. Further, the platform includes a chatbot creation program that allows a quick way to create a large number of customized chatbots without requiring advanced programming skills from the chatbot creator.

FIELD

This invention relates in general to electronic communications, and in particular, to a system and method for third-party-service-assisted chatbot workflow execution.

BACKGROUND

Development of communication via the Internet has transformed human lives in many areas, including how businesses interact with their customers. Whereas early Internet businesses have primarily relied on the user interface of their websites for communication with their customers when the communication did not have to be interactive, and on human agents acting via the Internet or another medium when an interactive two-way communication was necessary, the limitations of such communications became apparent over time. Thus, the number of customers that human agents can help is inherently limited, creating long wait times when the number of customers exceeds the number of available agents. Likewise, a customer trying to take an action, such as to receive information or order a particular product or service via a website, may be frustrated by how long completing the task and identifying correct information takes.

Chatbots, computer programs that can conduct a conversation with a human by executing a particular workflow, have recently made inroads into customer service. For example, automated online assistants include a chatbot that solicits input from a user and translates the input into a format that can be used by an expert system to find an answer to user queries. While such chatbots can increase the speed with which a customer receives assistance without requiring an increase in the number of human agents involved in customer service, the current chatbot technology still suffers from multiple drawbacks.

First, creating a chatbot customized for a particular business can require tremendous efforts and expertise, which may not be available to a majority of entities, such as individuals or business, in need of such a bot. The required resources increase along with the number of chatbots needed, and if an entity offers goods or services diverse enough to require multiple chatbots, getting the required chatbots may be unattainable.

Further, even if a chatbot is available to assist a customer, accessing such chatbot generally requires the customer to use specific software. Thus, a customer may be required to enter a particular chatroom or install a particular software. These technical requirements not only require a customer to spend additional time to interact with the chatbot, but may also prevent the customer from accessing the chatbot entirely if the computing device of the customer is not compatible with the technical requirements.

Finally, the answers that a chatbot can provide to a user are generally limited by the information stored internally by the system to which the chatbot interfaces. If the stored information is insufficient, the chatbot may not be able to assist the customer. Further, such chatbots generally lack any insight on the user, and may not customize their responses to the specific demands of a particular user. Finally, such bots usually employ a sequential conversation flow, and the speed with which the conversation proceeds is limited by the length of the sequence.

Accordingly, there is a need for a flexible way to facilitate interactions with chatbots that can leverage a plurality of sources of information and for an easy, scalable, way to produce such chatbots.

SUMMARY

The flexibility of a communication with a chatbot can be increased using a chatbot platform that can be integrated with a plurality of chat channels as well as facilitate communication between users of different chat channels. The platform can host chatbots that can leverage a plurality of resources, including internal and external natural language processors, machine learning, analytics services, and third party services to generate a response to user communications and take actions on behalf of the user. The use of the natural language processing and other additional information allows to generate an appropriate response to user queries, reducing the sequence of steps that needs to be taken, and thus increasing the speed with which user concerns are address. Further, the platform includes a chatbot creation program that allows a quick way to create a large number of customized chatbots without requiring advanced programming skills from the chatbot creator.

In one embodiment, a system and method for third-party-service-assisted chatbot workflow execution is provided. One or more communications from a computing device of a user are received by a platform, the platform including a plurality of servers and hosting a chatbot interfaced to a plurality of chat channels, the communications received via one of the chat channels at one the servers assigned as an endpoint for the chatbot, wherein each of the servers includes a processor and a memory, the chatbot is associated with a workflow requiring an interaction with a third party service outside of the platform, and one of the communications is coupled with a token proving that the user has logged into the third party service. Each of the communications is analyzed by the platform and one or more steps in the workflow that need to be taken in response to that communication are determined by the platform based on the analysis. The token is provided by the platform via the endpoint server to the third party service and one or more interactions with the third party service are performed by the platform based on one or more of the determined steps. A response to each of the communications is generated by the platform based on the analysis of that communication, wherein one or more of the responses are further generated based on one or more of the interactions with the third party service. The responses are formatted for transmission via the one chat channel. The responses are sent by the platform via the endpoint server and the one chat channel to the computing device.

Still other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein are described embodiments by way of illustrating the best mode contemplated for carrying out the invention. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modifications in various obvious respects, all without departing from the spirit and the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a system for facilitating computer-generated conversations in accordance with one embodiment.

FIG. 2 is a screenshot of the user interface of the chatbot creation program of FIG. 1 in accordance with one embodiment.

FIG. 3 is a screenshot of the user interface of the chatbot creation program of FIG. 1 showing workflow creation in accordance with one embodiment.

FIG. 4 is a diagram showing, by way of example, a plurality of possible modules that can be incorporated into a chatbot.

FIG. 5 is a flow diagram showing a method for facilitating computer generated conversations in accordance with one embodiment.

FIG. 6 is a flow diagram showing a routine for creating a chatbot for use in the method of FIG. 5 in accordance with one embodiment.

FIG. 7 is a flow diagram showing a routine for establishing multi-channel communication for use in the method of FIG. 5 in accordance with one embodiment.

FIG. 8 is a flow diagram showing a routine for running a chatbot for use in the method of FIG. 5 in accordance with one embodiment.

FIG. 9 is a database schema for use in the system of FIG. 1 in accordance with one embodiment.

DETAILED DESCRIPTION

FIG. 1 is a block diagram showing a system 10 for facilitating computer generated conversations in accordance with one embodiment. The system 10 includes one or more user devices 11 that can connect via a communication network 12 to one or more servers 13 executing one or more communication channels, via an interface such as a web-browser or a dedicated application. In particular, the computing device 11 can communicate via the communication channels with another party. Such communications can be based on input of a user, which can be a human user or a chatbot relaying the received information to a human end-user.

While the user device 11 is shown as a laptop, other kinds of user devices, such as desktop computers, smartphones, tables, and smart-watches, that can connect to a communication channel via a communication network 12 are possible. The communication network 12 can be a cellular network or the Internet, though other kinds of communication networks 12 are also possible.

The chat channels implemented by the servers 13 are services that can relay messages between two or more participants in a conversation. Examples of such channels include social networking chat services, such as Facebook® chat, as well as standalone messaging services, such as Skype®, Kik®, Telegram®, and SMS messaging services. Other kinds of chat channels are possible.

The chat channel servers 13 for each of the chat channels can generate a token 14, such as a Jason Web Token (JWT), and provide the token 14 to the computing device via the communication network 12. The computing device 11 can subsequently include the token 14 with all of the messages sent to that chat channel to verify the identity of the user of the computing device 11 and to make sure that a response communication is returned to the correct user.

As described further below, one more chatbots 16 can be registered with the chat channels, allowing a user of the chat channels to communicate with the chatbots 16 via the chat channel servers 13. Thus, by way of example, a user of the computing device 11 can search for chatbots 16 registered with a channel using the interface to that channel (such as the web-browser executing on the computing device 11 or the application running on the computing device 11), and select the chatbot 16 the user would like to communicate with, such as by typing in a hashtag associated with the selected chatbot 16 into the interface. Other ways to specify the chatbot 16 the user would like to conversate with are possible. Subsequently, after the user specifies to the chat channel services, the chatbot 16 that the user would like to communicate with, the messages sent from the computing device 11 during that conversation session would be forwarded by the chat channel servers 13 to the appropriate chatbot 16. The communication from the user of the computing device 11 can be in any format, including text, audio, or video communication. Further, the communication can be coupled with a request, such as a POST request in the HTTPS protocol, requesting the service 17 to accept the communication and to forward the communication to the selected chatbot 16.

The chatbots 16 are implemented as part of a chatbot platform 17, which can be implemented within a cloud-computing environment 18. Each chatbot 16 includes software modules that define the functionality of the chatbot 16 and a workflow associated with that chatbot 16, a series of steps that the chatbot 16 follows during a conversation with the user. In a further embodiment, the chatbot platform 17 can be implemented on dedicated servers in the same physical location. The cloud-computing environment can be a part of Amazon Web Services® offered by Amazon.com Inc. of Seattle, Washington, such as by being a part of Amazon® Elastic Load Balancer, though other kinds of cloud-computing environments are possible.

Upon receiving a communication directed to one of the chatbots 16 in the chatbot platform 17, one or more of the chat channel servers 13 will send the communication to the chatbot platform 17 via a communication network 15. The communication network 15 can be the Internet or a cellular network, though other kinds of communication networks 15 are possible. The communication network 15 can be the same network as the communication network 12, or a different network than the communication network 12.

The chatbot platform 17 includes one or more servers 19, each of which which is entry point and an exit point within the chatbot platform 17 for communications intended for and sent from a particular chatbot 16 (“webhook server 19). In one embodiment, each webhook server 19 can be a Node.js server, though other kinds of run-time environment can be executed on the server. Every chatbots 16 is associated with one of the webhook servers 19, and as further described below, when a chatbot 16 is registered with the chat channels, the chat channels are provided an address of the webhook server 19 designated for that chatbot 16. The webhook servers 19 receive the communication sent by the chat channel servers 13, and forward that communication for subsequent processing to other components of the platform 17. Upon the receipt of the communication, the webhook server 19 for a chatbot 16 that received the message performs an integrity check of the chat channel from which the communication was received via the communication network 15. Such integrity check can include checking that the chat channel is running properly, that the servers 13 implementing that chat channel are connected to the communication network 15, and that the requested chatbot 16 has been registered with the chat channel. Further, as part of the integrity check, the webhook server 19 would verify the token received with the communication with the issuer of that token (such as one of the chat channel servers 13) that the token received with the communication has indeed been issued by the issuer. The token issuer can also provide information about the user that the user that can be used by the chatbot 16 in generating the response. The integrity check of the channel can also be based on the received token and by verifying the IP address of the servers 13 from which the communication is received to make sure that the communication was received from the chat channel that the communication is purported to be from. Other kinds of integrity checks are possible.

If the integrity check is successful, the webhook server 19 passes the received communication to other components of the platform 17 for further processing. If the integrity check is failed, the webhook server 19 returns to the chat channel servers 13 an error message, and no further processing of the received message takes place. In addition, upon a successful completion of the integrity check, the webhook server 19 can retrieve metadata needed for the operation of the chatbot 16, such as metadata identifying an Internet address of the natural language processor employed by the chatbot 16. Other kinds of metadata is possible. For example, the metadata can include a token, such as a JWT token, necessary for logging into third party services 27 used by the chatbot 16. The metadata can be retrieved by the webhook server 19 sending a request for the data, such as HTTPS GET request, to a token service 33 storing the metadata, which can be part of the cloud-computing environment 18 or be outside the cloud-computing environment 18. In one embodiment, the token service 33 can be an OpenID® service, though other kinds of services are possible. Further, if the chatbot 16 needs to log-in into a third party service during the execution of the workflow for that chatbot 16, the webhook server 19 can interact with a log-in service 34, such as MS/AAD service, to perform the log-in. To perform the log-in the webhook server 19 can send a request, such as an HTTPS POST request, along with a token retrieved as part of the metadata, such as a JWT token associated with the chatbot 16, to the log-in into the service 34. The log-in service 34 in turn can return another token, such as another JWT token, verifying that the chatbot 16 has been logged into the appropriate service along with an appropriate request (such as HTTPS POST request). The received metadata and the token received from the log-in service can be stored in a local cache service 35, such as a REDIS® cache, interfaced to the chatbot platform 17, which allows a quick retrieval as necessary during the operation of the chatbot 16.

In addition, the webhook server 19 can store persistent data generated by the chatbot 16 in a persistent data storage service 36, such as the MongoDB® service, interfaced to the chatbot platform 17. Such persistent data can include data regarding the communications exchanged with the computing device 11 as well as other data solicited from the user of the computing device 11. The persistent storage service 36 can also be interfaced to the analytics service 26, allowing the analytics service 26 to access the persistent data in the storage service 36.

The received communication is passed from the webhook servers 19 to at least one web-server 20 with the chatbot platform 17, which can interpret the request that was included with the communication. In one embodiment, the web-server 20 can be an NGINX® distributed by NGINX® Software Inc. of San Francisco, California, though other kinds of web-servers 20 are also possible. Based on the request included with the communication, the web-server 20 determines the communication to include a message in need of a reply, and forwards the communication to one or more servers 21 implementing the chatbots 16 for subsequent processing.

The chatbot servers 21 implements a route parser 22, which determines the next step or steps in the workflow associated with the chatbot 16 that needs to be taken in response to the communication. Thus, the workflow could be thought of as a decision tree and the route parsing find the step in the decision tree that would need to be taken in response to the communication. For example, if the communication includes a greeting, the next step in the workflow could be to generate a return greeting and prompt the user to communicate further. As the format of communications from different channels differs from one another, the way route parsing is performed also differs depending on which chat channel the communication came from. Thus, while if communications that included identical messages from the user were received from different communication channels, the same step of the workflow would be determined as needing to be implemented. However, the way the step could be determined could different from channel to channel due to the differences in formatting of the communication.

The servers 21 further implement an intent parser 23 to determine an intent of the sender of the communication from the computing device 11. Such intent can include determining what language the communication was sent in and, thus the intent of the sender regarding what language the reply needs to be in. Further, when the sender's communication can have multiple meanings, the intent parser 23 can determine the most likely meaning. For example, if the communication includes a phrase “I want to find a golf club,” the communication could potentially have multiple meanings. Thus, the sender could be looking to buy a club to hit a golf ball. Alternatively, the sender could be looking for a club where the sender could play golf. Still another option would be that the sender is looking for a club of owners of Volkwagen® Golf® cars. The ambiguity in the meaning of the phrase can be resolved by the intent parser 23 in multiple ways. First, the intent analyzer 23 can employ a natural language processor to generate and send a clarifying question to the sender of the communication via the chat channel servers 13, and analyze the received response to determine the meaning of the communication. The natural language processor 24 can be executed by the chatbot servers 21. Alternatively, the chatbot servers 21 caTn access a third party natural language processing service 25, such as Siri®, though other third party natural language processing services are also possible. The third party natural language processing service 25 can be located in the same cloud computing environment 18 as the chatbot platform; alternatively, the third-party natural language processor could be in another location accessible through the communication network 15. In addition, the intent parser 23 can access an analytics service 26 that can store information about the user associated with the computing device 11 as well as previous interactions of the user with the chatbot platform 17, and leverage the accessed data to determine the intent by looking at the context in which the communication was sent. For example, if the user has previously communicated with the chatbot platform 17 regarding Volkwagen® Golf® cars, the intent parser can determine the intent of the communication to be about finding a club of owners of the cars.

The analytics service 26 can be a part of the cloud-computing environment 19 or be in another location accessible through the communication network 15 and stores data regarding previous interactions of the sender with the chatbot platform 17 and analysis of such service information. Such stored information can include, by way of example, how many interactions the sender previously had with the chatbot platform 17, the average length of these interactions, the average price of purchases that the sender has previously made using the chatbot, though other kind of stored information is possible. In a further embodiment, the information stored in the analytics service 26 can be from a third party, such as the sender's social network profile, and include details regarding a sender that are not directly related to his or her interaction with the chatbot platform 17.

Once the intent is determined, the communication is passed to the chatbot 16 for which the communication is intended. The chatbots 16 can be stored in a storage 29 coupled to the servers 21 and retrieved when a server 21 needs a particular chatbot 16 to respond to a user communication. The chatbots 16 can be stored in accordance with a schema shown with reference to FIG. 9 , also other schemas are possible. As described above, each chatbot 16 includes instructions to execute a workflow defined by the creator of that chatbot 16, a plurality of steps that define the interaction with a user and other parties during a conversation. As described above, a particular step or steps that need to be taken in response to a communication is determined during route parsing. The step in the workflow that needs to be taken defines how the response is generated in combination with other factors. One such factor is the intent of the response communication that has been determined. If additional interpretation is needed, the chatbot 16 can use either the internal natural language processor 24 or the third party natural language processing service 25 to interpret the message, and to determine an appropriate response using the predefined workflow. In addition, the chatbot 16 can include a machine learning module (not shown), which can be trained, either on previous interactions with users or on other kinds of training samples, to classify the sender of the communication, either using through analysis of the message or using the information regarding the user obtained from the analytics service 26. For example, if in the communication, the sender of the message is asking to show options for preparing a tax return and states that he has a certain income, the machine learning module would classify the sender as falling into a certain tax bracket, and execute the step or steps in the workflow to present the sender the message with the options for GLa person falling into that tax bracket. Likewise, if the sender's income is accessed through the analytics service 26, the machine learning module can make the same classification. Further, additional information from the analytics service 26 can further impact the execution of the step or steps in the workflow. Thus, if the sender requests information regarding products that can fall within a wide range of prices, even if the chatbot 16 is in possession of the information that the sender is a high-income earner, if the analytics service provides that in the past, the sender has purchased the cheapest available products, the chatbot 16 would execute the workflow to generate the response communication that would include the cheapest available options.

As part of the execution of a workflow, the chatbot 16 can utilize one or more application programming interfaces (APIs) included in the chatbot 16 for interacting with third party services 27 that are accessible over the communication network 15 regardless of whether they are in the cloud-computing environment 18. Such interactions can include obtaining third party information for inclusion into the generated response message or for taking an action based on the user message. The third party services 27 can in turn include an API for interacting with the chatbot 16 API. For example, if the received communication includes a request for local weather, the chatbot 16 can retrieve weather data from a third party weather service. Likewise, if a user requests information for available flights for a particular date from Seattle, WA to San Francisco, CA, the chatbot 16 would through the appropriate API to request the information from a travel service allowing online booking of flights and include the received information into the response communication. Upon receiving a further communication that includes the sender's choice for one of the flights, the chatbot 16 can request the user's personal information necessary for booking a flight and payment information of the sender, such as a credit card information necessary to pay for the flight. The chatbot 16 receive the details and the information in subsequent messages from the computing device 11 and would use the personal details and the payment details to book the selected flight, and upon receiving confirmation details from the third party service 27, include the confirmation details into the response communication that is sent to the user.

The chatbots 16 can further interact with still other services, either within the cloud-computing environment or outside of the cloud-computing environment 15 and use the results of the interaction for generating the response communication. For example, the chatbot 16 can interact with an enterprise software service 38 that integrates information from a plurality of line-of-business applications. In one embodiment, the service 38 can be Enterprise Cloud Connect™ service provided by SmarTek21, LLC, of Kirkland, WA. Other enterprise software services are possible 38. Still other services with which the chatbot 16 can interact are possible.

As described above, the result of a running of a chatbot 16 is a response communication that is sent to the computing device 11 via the same chat channel that the initial communication was received from. The chatbot servers 21 further execute a communication formatter 37, which prior to the communication being sent out to the computing device 11, is formatted for the requirements of the communication channel via which the response communication will be sent. Thus, if the response communication will be made via Skype®, the response communication is formatted into the format (such as a particular kind of a JSON object) appropriate for transmission via Skype®. As mentioned above, the communication sent from the computing device 11 can be in any medium, including text, video, and audio. Similarly, the response communication can be in any medium, including text, video, and audio.

Once the response communication is formatted by at least one of the chatbot servers 21, the response communication is sent by the chatbot server 21 to the webhook server that is associated to the chatbot 16 that generated the message and into which the incoming communication for the chatbot 16 was initially received. The webhook server 19 in turn sends the response communication to the computing device 11 via the communication networks 12, 18 and the chat channel servers 13. The response communication is sent along with the token 14 associated with the user, which the chat channel servers 13 can use for forwarding the response communication to the computing device 11 of the user. The response communication can also be coupled to a request in a computing language, such as an HTTPS POST request, directing the chat channel servers 13 to forward the communication to the computing device 11. The chatbot 16 can further retrieve information about the received communication and the communication sent in the analytics service 26.

While the sender of the communication can use a conversation with a chatbot 16 to obtain information or to perform another online action, the chatbot platform 17 can also be used to facilitate conversation between multiple users who are using multiple communication channels. The conversation can begin by a first user requesting one of the chat channel servers 13 to create a chatroom. The request can be made before or after the user selects to talk to a chatbot 16. The chatroom is associated with an identifier, which is conveyed by one of the chat channel servers to the chatbot platform 17 via the communication network 15. The chatbot platform 17 can in turn provide the identifier to other chat channels with which the chatbot 16 is registered. Subsequently, a second user, using a second computing device 30 and a second chat channel can select the chatroom, such as by searching identifiers of chatrooms that have been communicated to the different chat channel as being used for the conversation with the chatbot 16 in question. The communications posted by the first user into the chatroom are forwarded to the chatbot 16 by the chat channel servers 13 for the channel used for hosting the chatroom, as described above. Upon receiving the message, at least one chatbot server 21, using at least one of the chatbot 16 and the formatter 37, formats the received communication for transmission to the second chat channel and sends the formatted communication to the second user via the second chat channel. Likewise, the communications sent by the second user to the chatbot platform 17 via the second chat channel, are formatted for transmission to the first communication channel and sent by the chatbot platform 17 to the first communication channel for posting in the chatroom. Thus, the communications posted by the first user in the chatroom are forwarded by the chatbot platform 17 to the second user, and the communications sent by the second user are sent for posting in the chatroom, allowing both users to see each other's communications despite using different communication channels. While in the above description, the chatbot platform 17 acts as merely a relay, in a further embodiment, the chatbot 16 can generate a response communication to the communications from each the users and provide that response communications to each of the users. While in the example above, only two users are involved, any number of users of any number of differing chat channels with which a chatbot 16 is registered can participate in a multi-channel conversation via the facilitation of the chatbot platform 16.

In addition to providing for a quick and efficient way to obtain desired information and perform user actions, the chatbot platform 17 also provides a scalable way to create chatbots 16 with desired properties without requiring specialized programming knowledge from a user. Thus, a creator of one of the chatbots 16 can connect via the communication network 15 to one or more chatbot creation servers 31 that implement a chatbot creation program 32 via computing device 38, which provides a user interface for defining characteristics of a chatbot 16 that the user desires to create. FIG. 2 is a screenshot of the user interface 40 of the chatbot creation program 32 of FIG. 1 in accordance with one embodiment. The user interface 40 includes a window 41 into which the chatbot creator can enter the desired name of the chatbot 16, a description of the chatbot that could be displayed to an end-user, and an image associated with the chatbot 16 that could be displayed to the end-user. The user interface 40 further provides a way for the user to define the steps of the workflow that will be executed by the chatbot 16. FIG. 3 is a screenshot of the user interface 40 of the chatbot creation program 32 of FIG. 1 showing workflow creation in accordance with one embodiment. As can be seen with reference to FIG. 3 , a user can visually link each of the steps in the workflow, test the execution of each of the steps, configure what happens during each of the steps, and define fallback steps for that step, such as a step that is done if a particular chat channel is not compatible with the current step. In addition, through windows of the user interface that are not shown, the user can enter the channels that the creator would like to enter the chatbot 16 to be registered with as well as creator preferences for configuring the chatbot on each of the selected channels. Thus, among the configuration preferences, the creator can define how the chatbot will be represented within the chat channel, such as the amount of details regarding a product advertised by the chatbot 16 that will be displayed, elements of the user interface, how the page in the chat channel will look into which the user can enter payment details, and whether additional APIs can be called when the particular chat channel is used. In addition, as further defined with reference to FIG. 4 , the creator can select one or more predefined software modules that impart the chatbot 16 being created desired functionality.

Upon receiving the user preferences from the creator of the chatbot 16, the chatbot creation program 32 compiles the chatbot 16 based on the input. The chatbot creation program 32 also assigns one of the webhook servers 19 as the endpoint for the new chatbot 16 to which the communications directed to that bot arrive and from which the communications from that chatbot leave. The chatbot creation program 32 further generates credentials for the chatbot 16, such as an identifier of the chatbot, which can be an alphanumeric identifier or another kind of identifier, and a password necessary for making changes to or otherwise managing the developed chatbot 16. The chatbot 16 is configured for each of the chat channels selected by the creator by the chatbot creation program 32 and an exchange of messages between the chatbot 16 and the channels is performed under the control of the chatbot creation program 32. The URL of the endpoint (webhook server 19) of the configured chatbot as well as chatbot description, name, and image, are provided to the channel servers 13, allowing the channel servers 13 to describe the chatbot 16 to the users of the communication device 11 and to contact the chatbot 16 when necessary. The created chatbot is stored by the chatbot servers, the retrieval of the chatbot 16 when running the chatbot 16 is necessary.

As mentioned above, in creating the chatbot 16, the user can select predefined modules that will impart a specific functionality on the newly-created chatbot 16. FIG. 4 is a diagram showing, by way of example, a plurality of possible modules that can be incorporated into a chatbot 16. Each of the modules is a computer program or procedure written as source code in a conventional programming language that can be presented for execution by the central processing unit as object or byte code. By way of example, the modules can include a cache module for interacting with a local cache; a city image module for retrieving from a third party service 27 images of a particular city and including them in a response communication; a Wego module for interacting, such as via booking flights and obtaining flight information, with the third party travel service 27 Wego™; one or more natural language processors; a Salesforce Module for interacting with another third party service 27, cloud-computing service Salesforce®; a logger module for recording data; a weather module for accessing weather data from a third party weather service 27; an analytics module for accessing data from the analytics service 26; and a database module for storing data in a database. The modules are described only by way of examples, and other modules that can be incorporated into chatbots 16 are possible.

The servers 13, 19, 21,31 can each include one or more modules for carrying out the embodiments disclosed herein. The modules can be implemented as a computer program or procedure written as source code in a conventional programming language and that is presented for execution by the central processing unit as object or byte code. Alternatively, the modules could also be implemented in hardware, either as integrated circuitry or burned into read-only memory components, and each of the servers 32 can act as a specialized computer. For instance, when the modules are implemented as hardware, that particular hardware is specialized to perform the modeling and notification and other computers without the hardware cannot be used for that purpose. The various implementations of the source code and object and byte codes can be held on a computer-readable storage medium, such as a floppy disk, hard drive, digital video disk (DVD), random access memory (RAM), read-only memory (ROM) and similar storage mediums. Other types of modules and module functions are possible, as well as other physical hardware components.

While the services 25, 26, 33, 34, 35, and 36 are shown to be within a cloud-computing environment 17, in a further embodiment, the services can be implemented differently. Thus, the various services described above, such as the cache service 35, the persistent memory service 36, the token service 33, the log-in service 34, the natural language processor services 25, enterprise software services 35, analytics services 26, and third party services 27 can be implemented by the hardware, such as servers and databases, within the cloud-computing environment 18 or by dedicated hardware.

The chatbot platform 17 can further implement a plurality of security measures, including executing a firewall by the webhook servers 19, as well as requiring the user to perform additional log-in protocols. For example, if the user has an account with a particular third party service 27 accessing which is necessary for the operation of the chatbot, upon the user selecting to send messages to a particular chatbot 16 in a particular chat channel, the user can be prompted to log-in into the third party service 27 via the chat channel. If the log-in successful, an ID or another token proving the successful log-in is coupled to the communication sent to the chatbot platform 17. In turn, the chatbot platform can provide include the ID in all calls to the third party service 27, proving that the user has logged-in into that third party service.

Other security measures, such a use of encryption of data being passed from the chatbot 16 to the computing device via the chat channel as well as encryption of user data otherwise present in the platform is also possible.

The chatbot platform facilitates interactions with a user over a variety of communication channels and can in turn interact with a variety of third party services, providing the flexibility necessary to quickly and efficiently to communicate with an end-user and accomplish a variety of user-defined tasks. FIG. 5 is a flow diagram showing a method 60 for facilitating computer generated conversations in accordance with one embodiment. The method 60 can be implemented using the system 10 of FIG. 1 , though other implementations are also possible. Optionally (if no chatbots are stored on the chatbot platform, the step is required), one or more chatbots are created and registered with the communication channels based on user input, as further described below with regards to FIG. 6 (step 61). A communication from a computing device is received by the webhook service associated with the chatbot requested by the sender of the communication via at least one chat channel (step 62). The received communication can be coupled with a token that can be used for verification of the user of the computing device that sent the communication. The communication can also be coupled with a request, such as a request written in HTTPS protocol, to process the communication.

An integrity check is performed by the webhook server associated with the chatbot (step 63). The integrity check can include checking that the chat channel is correctly functioning, is compatible with the requested chatbot. The integrity check can also include checking the integrity of the communication. The integrity check can further involve verifying the token received with the issuer of that token. The integrity check can be token-based (using the token coupled to the communication) and IP address based, allowing to verify that the communication arrived from the IP address associated with the chat channel from which the communication is purported to be from. If the integrity check is failed (step 64), the webhook server returns an error message to the chat channel from which the communication came (step 65). If additional communication is sent to the chatbot platform (step 66), the method returns to step 62. If no additional communications are sent (step 66), the method 60 ends.

If the integrity check is passed (step 64), whether multi-channel communication was requested by the sender of the communication by the webhook server (step 67). If the multi-channel communication was requested (step 67), the multi-channel communication is established as further described below with reference to FIG. 7 (step 68). In a further embodiment, whether multi-channel communication is requested can be determined at a different point in the method 60. If no multi-channel communication was requested (step 67), the method 60 moves to step 69. Metadata necessary for running the chatbot 16 is retrieved and cached In a local cache (step 69), and, optionally, log-in of the chatbot into any third-party servers necessary for running the chatbot, with any tokens received from the log-in also being cached in the local cache (step 70). A route in the workflow associated with the chatbot is parsed, determining what next step or steps in the workflow is to be taken by the chatbot in response to the communication, with the route parsing being done based on the chat channel through which the communication was received due to the differences in formatting of the communications received through the different channels (step 71). The communication is analyzed to determine intent of the sender of the communication, such as by leveraging natural language processing or by determining the context in which the communication was sent using the data retrieved from an analytics service, as further described above with reference to FIG. 1 (step 72). The chatbot to which the communication is addressed is retrieved from storage (if the retrieval has not already been previously done) and run, as further described with reference to FIG. 8 , generating a response communication (step 73). The generated communication is formatted into a format appropriate for the chat channel over which the communication was received (step 74). The response communication is sent to the computing device over the same chat channel through which the incoming message is received by the same webhook server that received the incoming communication, ending the message (step 75). If multi-channel communication was established, the response message and the initial communication are also formatted in step 75 for distribution to one or more users over one or more additional communication channels. In a further embodiment, if chatbot platform only acts as a relay for the additional communication, steps 71 and 72 could be skipped, and no response communication is generated during the running of the chatbot, with the chatbot only identifying the users to whom the received communication should be relayed.

Following the sending of the response message, if no further communications are received from the user (step 66), the method 60 ends. If further communications are received (step 66), the method 60 returns to step 62.

Providing a visual way to create the chatbots allows to easily build a large number of such chatbots without advanced programming skills. FIG. 6 is a flow diagram showing a routine 80 for creating a chatbot for use in the method 60 of FIG. 5 in accordance with one embodiment. Initially, user input for creating the chatbot is received at by the chatbot platform (step 81). Such input can include a desired name of the chatbot being created, a description of the chatbot that could be displayed to an end-user, an image associated with the chatbot 16 that could be displayed to the end-user, chat channels with which the bot needs to be registered, chat channel configuration preferences, the workflow which the chatbot needs to execute, and the modules that define the functionality of the chatbot. Other input is possible. The chatbot is compiled based on user input (step 82). The chatbot is assigned an endpoint within the chatbot platform, one of the webhook servers which will receive the messages addressed for that chatbot and from which the messages from that chatbot will be sent (step 83). Credentials, such as identifier and password, are generated for the chatbot, as further described above (step 84). The chatbot is registered with and configured for interaction with the chat channels, as further described above (step 85). The chatbot is stored on the chatbot platform in the storage, while the data associated with the chatbot 16 can also be stored in the services interfaced to the platform, such as the token service as described above (step 86), ending the routine 70.

Multi-channel communication allows users who employ different communication channels to talk to each other without having to sign up to use each other's communication channels. FIG. 7 is a flow diagram showing a routine 90 for establishing multi-channel communication for use in the method 60 of FIG. 5 in accordance with one embodiment. An identifier of a chatroom that the sender of the received communication has established in the chat channel over which the communication arrived is received by the webhook server associated with the chatbot (step 91). The chatbot provides the identifier to other chat channels with which the chatbot is registered (step 92), allowing the users of the chat channels to request communication via the chatroom. The chatbot receives one or more additional requests from one or more additional users of different communication channels (step 93), ending the routine 80. As described above, based on the received requests, the chatbot will relay the messages between the users using the chatroom.

The chatbot can leverage multiple, internal and external services, to generate the response communication that addresses the user's needs in the most helpful and efficient fashion. FIG. 8 is a flow diagram showing a routine 100 for running a chatbot for use in the method 60 of FIG. 5 in accordance with one embodiment. Optionally, if necessary for additional analysis of the communication, the chatbot applies natural language processing to the communication, either via an internal natural language processor or an external natural language processor (step 101). Also, optionally, the accesses information regarding the sender of the communication from an analytics service to which the chatbot is interfaced (step 102). Optionally, the classifier can perform a machine-based learning classification based on the data in the communication, and the data received from the analytics service (step 103). Optionally, the chatbot interacts with a third party service, receiving additional information or taking action based on the communication, such as booking a flight for the sender of the message, as further described above (step 104). Based on the results of one or more of the steps 101-104, the step or steps in the workflow that is determined during route parsing (step 71), and the determined intent (step 72), the chatbot generates a response communication (step 105), ending the routine.

While the invention has been particularly shown and described as referenced to the embodiments thereof, those skilled in the art will understand that the foregoing and other changes in form and detail may be made therein without departing from the spirit and scope of the invention. 

What is claimed is:
 1. A system for third-party-service-assisted chatbot workflow execution, comprising: a platform comprising a plurality of servers, each of the servers comprising a processor and a memory, the platform hosting a chatbot registered with a plurality of chat channels and associated with a workflow requiring an interaction with a third party service outside of the platform, the platform configured to: receive via one of the chat channels at one of the servers assigned as an endpoint for the chatbot one or more communications from a computing device of a user, wherein one of the communications is coupled with a token proving that the user has logged into the third party service; analyze each of the communications and determine one or more steps in the workflow that need to be taken in response to that communication based on the analysis; provide via the endpoint server the token to the third party service and perform one or more interactions with the third party service based on one or more of the determined steps; generate a response to each of the communications based on the analysis of that communication, wherein one or more of the responses are further generated based on one or more of the interactions with the third party service; format the responses for transmission via the one chat channel; and send the responses via the endpoint server and the one chat channel to the computing device.
 2. A system according to claim 1, wherein the user is prompted to log into the third party service via the one chat channel.
 3. A system according to claim 1, the platform further configured to provide to the third party service a portion of one or more of the communications.
 4. A system according to claim 1, the platform further configured to receive from the third party service data and to include the received data in one of the response communications.
 5. A system according to claim 1, wherein the chatbot comprises an application programming interface for interacting with the third party service.
 6. A system according to claim 1, the platform further configured to determine an intent of the user associated with one or more of the communications, wherein the steps associated with those communications are determined based on the intent associated with those communications.
 7. A system according to claim 6, the platform configured to interact with one or more further services outside of the platform to determine the intent.
 8. A system according to claim 7, the platform configured to retrieve metadata necessary for interaction with one or more further services.
 9. A system according to claim 8, wherein the platform interacts with one of the further services to obtain the metadata for the interaction with another one of the further services.
 10. A system according to claim 8, the platform configured to store the metadata in a local cache upon retrieving the metadata.
 11. A method for third-party-service-assisted chatbot workflow execution, comprising: receiving by a platform, the platform comprising a plurality of servers and hosting a chatbot interfaced to a plurality of chat channels, via one of the chat channels at one the servers assigned as an endpoint for the chatbot one or more communications from a computing device of a user, wherein each of the servers comprises a processor and a memory, the chatbot is associated with a workflow requiring an interaction with a third party service outside of the platform, and one of the communications is coupled with a token proving that the user has logged into the third party service; analyzing by the platform each of the communications and determining by the platform one or more steps in the workflow that need to be taken in response to that communication based on the analysis; providing by the platform via the endpoint server the token to the third party service and performing by the platform one or more interactions with the third party service based on one or more of the determined steps; generating by the platform a response to each of the communications based on the analysis of that communication, wherein one or more of the responses are further generated based on one or more of the interactions with the third party service; formatting by the platform the responses for transmission via the one chat channel; and sending by the platform the responses via the endpoint server and the one chat channel to the computing device.
 12. A method according to claim 11, wherein the user is prompted to log into the third party service via the one chat channel.
 13. A method according to claim 11, further comprising providing by the platform to the third party service a portion of one or more of the communications.
 14. A method according to claim 11, further comprising receiving by the platform from the third party service data and including by the platform the received data in one of the response communications.
 15. A method according to claim 11, wherein the chatbot comprises an application programming interface for interacting with the third party service.
 16. A method according to claim 11, further comprising determining an intent of the user associated with one or more of the communications, wherein the steps associated with those communications are determined based on the intent associated with those communications.
 17. A method according to claim 16, further comprising interacting by the platform with one or more further services outside of the platform to determine the intent.
 18. A method according to claim 17, further comprising retrieving by the platform metadata necessary for interaction with one or more further services.
 19. A method according to claim 18, wherein the platform interacts with one of the further services to obtain the metadata for the interaction with another one of the further services.
 20. A method according to claim 18, further comprising storing by the metadata in a local cache upon retrieving the metadata. 